home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
4_1_06.tro
< prev
next >
Wrap
Text File
|
1991-12-13
|
76KB
|
3,447 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright ( c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v | 5i'
.LP
\fBMONTAGE:\ \fR DEBUT DE REC.\ 140 EN T\* | TE DE CETTE PAGE
.sp 2P
.LP
\v'13P'
\fB8\fR \fBDesignations of international digital blocks
(bidirectional and unidirectional)\fR
.sp 1P
.RT
.sp 1P
.LP
8.1
\fIGeneral\fR
.sp 9p
.RT
.PP
This section refers to blocks which are part of the digital
multiplex hierarchy and which are formatted according to
Recommendations\ G.734, G.736, G.742, G.743, G.745, G.751, G.752, G.753
and\ G.754\ [10]. All other blocks are designated according to \(sc\ 11.
.PP
The format of the designation of digital blocks is shown in
Table\ 6/M.140.
.RT
.ce
\fBH.T. [T6.140]\fR
.ce
TABLE\ 6/M.140
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(24p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | lw(18p) | cw(24p) | cw(18p) .
Format of designation Town A / {
Suffix for transmission station or international exchange
(optional)
} \(em Town B / {
Suffix for transmission station or international exchange
(optional)
} Function code Serial number
_
.T&
cw(24p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
Signs Characters Slash Letters/ digits Hyphen Characters Slash Letters/ digits Space Letters/ digits Digits
_
.T&
cw(24p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
Number of characters \(= 12 1 \(= 3 1 \(= 12 1 \(= 3 1 3\(hy6 \(= 4
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 6/M.140 [T6.140], p.\fR
.sp 1P
.RT
.ad b
.RT
.PP
The elements of the format are as follows:
.LP
a)
\fITraffic relation\fR
.LP
Town A and town B, possibly with a suffix for the
transmission station or international exchange, indicate the terminal points
of the block. For the spelling, see \(sc\ 1.1. If a town name exceeds the
maximum
length of 12\ characters, the Administration should apply a suitable
abbreviation which must be unique (see \(sc\ 0.1). The town names are arranged
in alphabetical order.
.LP
The suffix for the transmission station or international
exchange (maximum 3\ characters) is an optional field which may be used to
further identify the terminal point when there is more than one carrier
operating in the town. The necessity for a suffix and its form should be
decided by the Administration operating the circuit in the town concerned.
.LP
In the case of a multiple destination undirectional block, town\ B is
replaced by (MU) (see\ \(sc\ 8.4).
.bp
.LP
b)
\fIFunction code:\fR
.LP
This code consists of a number indicating the nominal number of channels
in the block followed by the letter\ N.
.LP
For blocks in a mixed analogue/digital environment, see
\(sc\ 10.1.2. (In this case 6\ characters or less are required.)
.LP
c)
\fISerial number\fR
.LP
This is a 1 to 4 digit number which counts the number of
blocks with the same traffic relation and the same function code.
.sp 1P
.LP
8.2
\fIBidirectional digital blocks\fR
.sp 9p
.RT
.PP
These blocks are designated according to the principles stated in \(sc\ 8.1.
.PP
\fIExample\ 1:\fR
.RT
.LP
The fourth secondary order block between London and Paris is
designated:
.LP
London\(emParis 120N4.
.LP
\fIExample\ 2:\fR
.LP
The tenth primary order block between New York and Tokyo is
designated:
.LP
New York\(emTokyo 24N10.
.sp 1P
.LP
8.3
\fIRestoration digital blocks\fR
.sp 9p
.RT
.PP
Digital blocks set up on restoration digital paths or spare
digital paths for restoration purposes will receive a serial number from the
800\ series, in descending order and starting from\ 899.
.PP
\fIExample:\fR
.RT
.LP
The first fourth order restoration block between Koebenhavn and Stockholm
is designated:
.LP
Koebenhavn\(emStockholm 1920N899.
.sp 1P
.LP
8.4
\fIMultiple destination unidirectional digital blocks\fR
.sp 9p
.RT
.PP
For these blocks the traffic relation is composed of the name of
the sending terminal station followed by a hyphen and the letters\ MU (Multiple
destination Unidirectional) in parentheses.
.PP
\fIExamples:\fR
.RT
.LP
The first multiple destination unidirectional primary digital block from
Bercenay (to, for example, London and Bruxelles) is designated:
.LP
Bercenay\(em(MU) 30N1.
.LP
The next multiple destination unidirectional primary digital
block from Bercenay (to, for example, Frankfurt and Roma) is designated:
.LP
Bercenay\(em(MU) 30N2.
.LP
\fINote\fR \ \(em\ Digital blocks routed via a multi\(hyaccess system may
be provided for exclusive use between two terminal stations only, in which
case the normal designations given above in this Recommendation will apply.
.sp 1P
.LP
8.5
\fISingle destination unidirectional digital blocks\fR
.sp 9p
.RT
.PP
These blocks are designated as normal digital blocks and numbered in the
same sequence. The unidirectional property as well as the direction of
transmission has to be registered in Related Information under item\ 16
(Direction of transmission, see \(sc\ 12.16).
.PP
\fIExample:\fR
.RT
.LP
A unidirectional primary digital block transmitting in the
direction Roma to London, which is the 21st primary digital block on that
relation is designated:
.LP
London\(emRoma 30N21.
.sp 1P
.LP
8.6
\fIRelated information\fR
.sp 9p
.RT
.PP
The additional information on digital blocks is covered by the
following items:
.RT
.LP
1.
Urgency for restoration;
.LP
2.
Terminal countries;
.LP
3.
Administrations', carriers' or broadcasting companies'
names;
.bp
.LP
4.
Control and sub\(hycontrol station(s);
.LP
5.
Fault report points;
.LP
6.
Routing:
.LP
7.
Association;
.LP
8.
Equipment information;
.LP
9.
Use;
.LP
10.
Transmission medium information;
.LP
11.
(Empty item, use: \*Q\(em;\*U);
.LP
12.
Bit rate;
.LP
13.
Occupancy;
.LP
14.
Actual number of channels (for primary blocks only);
.LP
15.
Clocking information;
.LP
16.
Direction of transmission (for unidirectional blocks
only);
.PP
The various items will be dealt with in \(sc\ 12.
.sp 2P
.LP
\fB9\fR \fBDesignation of international digital paths\fR
.sp 1P
.RT
.PP
In practice it may be that terminal equipment is not connected to a digital
path. Nevertheless, for designation purposes the digital path will
be designated as though digital blocks had been set up (see \(sc\ 8.1).
.RT
.sp 1P
.LP
9.1
\fIConventional digital paths not connected to their terminal\fR
\fIequipment\fR
.sp 9p
.RT
.PP
Such digital paths are included in the normal serial numbering
sequence of digital blocks and are not given a separate numbering
sequence.
.RT
.sp 1P
.LP
9.2
\fIRestoration digital paths\fR
.sp 9p
.RT
.PP
Digital paths nominated for restoration purposes are designated by serial
numbers taken from the 800\ series in ascending order and starting
from\ 801.
.RT
.LP
Restoration paths for first order digital blocks: 30N801,
30N802,\ etc.
.LP
Restoration paths for second order digital blocks: 120N801,
120N802,\ etc.
.LP
\fIExample\ 1:\fR
.LP
The 4th second order restoration digital path between London
and Paris is designated:
.LP
London\(emParis 120N804.
.LP
\fIExample\ 2:\fR
.LP
The first third order restoration digital path between
Amsterdam and Paris is designated:
.LP
Amsterdam\(emParis 480N801.
.sp 1P
.LP
9.3
\fIDigital line sections and digital radio sections\fR
.sp 9p
.RT
.PP
Designations of digital line sections and digital radio sections
are under consideration.
.RT
.sp 1P
.LP
9.4
\fIRelated Information\fR
.sp 9p
.RT
.PP
The additional information on digital paths is covered by the
following items:
.RT
.LP
1.
Urgency for restoration;
.LP
2.
Terminal countries;
.LP
3.
Administrations', carriers' or broadcasting companies'
names;
.LP
4.
Control and sub\(hycontrol station(s);
.LP
5.
Fault report points;
.LP
6.
Routing;
.LP
7.
Association;
.LP
8.
Equipment information;
.bp
.LP
9.
Use;
.LP
10.
Transmission medium information;
.LP
11.
(Empty item, use: \*Q\(em;\*U);
.LP
12.
Bit rate;
.PP
The various items will be dealt with in \(sc\ 12.
.sp 2P
.LP
\fB10\fR \fBDesignations of routes\fR
.FS
This term is used provisionally
in this context to designate various combinations of analogue and digital
sections with appropriate intermediate equipment and usually also including
terminal equipment, as illustrated in Figure\ 2/M.140 and Figure\ 3/M.140.
.FE
\fBin the mixed analogue/digital transmission network\fR
.sp 1P
.RT
.PP
Conforming to the philosophy for lining\(hyup and maintaining a mixed analogue/digital
transmission network (Recommendation\ M.20), the analogue and digital parts
of the network are designated separately. To indicate that the
end\(hyto\(hyend transmission relies on a mixture of analogue and digital
transmission systems, the letter\ C is included in both the analogue and
digital designations. The funcion code may, therefore, consist of a maximum
of
6\ characters.
.PP
Transmultiplexer equipment is included in the designation of the
analogue part of the route.
.RT
.sp 2P
.LP
10.1
\fITransmission routes with one analogue\(hyto\(hydigital\fR
\fIconversion\fR
.sp 1P
.RT
.sp 1P
.LP
10.1.1
\fIGroups and supergroups, etc., forming part of a mixed\fR
\fIanalogue/digital transmission route\fR
.sp 9p
.RT
.PP
Groups, supergroups, etc., which are converted into digital paths at some
point are designated in the same way as conventional groups or
supergroups (see \(sc\ 5.1), but have a letter\ C included in the function
code and placed after the nominal number of channels.
.PP
\fIExamples:\fR
.RT
.LP
Group:
London\(emRiyadh 12C02
.LP
Amsterdam\(emKoebenhavn 12C899
.LP
(restoration group)
.LP
Supergroup:
Paris\(emSydney 60C01
.LP
Mastergroup:
Bruxelles\(emLondon 300C03
.LP
Supermastergroup:
Amsterdam\(emParis 900C04
.PP
Figure 2/M.140 shows a typical analogue/digital arrangement and
how it will be designated.
.sp 1P
.LP
10.1.2
\fIDigital blocks and paths forming part of a mixed\fR
\fIanalogue/digital transmission route\fR
.sp 9p
.RT
.PP
Digital blocks and paths which are converted into analogue groups, supergroups,\
etc., at some point are designated in the same way as conventional digital
blocks and paths, but have an additional letter\ C placed after the
letter\ N.
.PP
\fIExample:\fR
.RT
.LP
Madrid\(emRome 480NC1.
.PP
Figure 2/M.140 shows a typical analogue/digital arrangement and
how it will be designated.
.sp 1P
.LP
10.1.3
\fIEnd\(hyto\(hyend designations\fR
.sp 9p
.RT
.PP
This subject is covered by item\ 11 in Related Information for
digital blocks (see \(sc\ 12.11).
.RT
.sp 2P
.LP
10.2
\fITransmission routes with two analogue\(hyto\(hydigital\fR
\fIconversions\fR
.sp 1P
.RT
.sp 1P
.LP
10.2.1
\fIEnd\(hyto\(hyend designations\fR
.sp 9p
.RT
.PP
Where both ends of a route involving two analogue\(hyto\(hydigital
conversions are analogue, an end\(hyto\(hyend designation using the analogue
notation described in \(sc\ 10.1.1 should be agreed between the terminal
Administrations.
.bp
.PP
Where both ends are digital, an end\(hyto\(hyend designation using the
digital notation described in \(sc\ 10.1.2 should be agreed between the
terminal
Administrations.
.PP
By the above means, both terminal stations have available a common
designation for the end\(hyto\(hyend transmission route, and are informed
of its
mixed analogue/digital nature.
.RT
.sp 1P
.LP
10.2.2
\fIIntermediate section designation\fR
.sp 9p
.RT
.PP
The intermediate part of the route is given a separate designation using
the appropriate notation. The choice of this designation is the
responsibility of the Administrations providing the intermediate part of the
route, and it is their responsibility to associate, in their records, this
intermediate designation with the overall designation.
.PP
Figure 3/M.140 shows two examples of routes involving two
analogue\(hyto\(hydigital conversions and how they will be designated.
.RT
.LP
.rs
.sp 42P
.ad r
\fBFigure 2/M.140, p. 2\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 40P
.ad r
\fBFigure 3/M.140, p. 3\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
10.3
\fITransmission routes with more than two analogue\(hyto\(hydigital\fR
\fIconversions\fR
.sp 9p
.RT
.PP
The transmission planning rules given in Recommendation\ G.113,
\(sc\ 3\ [11] effectively restrict the number of unintegrated digital processes
(e.g.\ analogue\(hyto\(hydigital conversions) permitted in the international
part of a telephone connection. Similarly, the routing plan given in
Recommendation\ E.171\ [12] restricts the number of international circuits
in a connection to four.
.PP
In view of these rules it is desirable to limit the number of
analogue\(hyto\(hydigital conversions in each direction between international
centres to a maximum of two. Therefore the detailed designation requirements
of routes with more than two analogue\(hyto\(hydigital conversions are
not considered.
.RT
.sp 1P
.LP
10.4
\fIRelated Information\fR
.sp 9p
.RT
.PP
The additional information on groups and blocks in the mixed
analogue/digital network is covered by the same items as analogue groups and
digital blocks respectively. However the item\ 11, \*QEnd\(hyto\(hyend
information\*U is used in addition (see \(sc\(sc\ 7.11 and\ 12.11).
.bp
.RT
.sp 2P
.LP
\fB11\fR \fBDesignation of data transmission systems\fR
.sp 1P
.RT
.sp 1P
.LP
11.1
\fIGeneral\fR
.sp 9p
.RT
.PP
This section deals with data transmission systems provided between the
premises of Administrations. (Those between renters' premises are
designated according to \(sc\ 3.2.15 concerning digital leased circuits
connecting two locations.)
.PP
The designation scheme of these data transmission systems can only be used
if they are non\(hyhierarchical or not formatted according to the
Recommendations\ G.734, G.736, G.742, G.743, G.745, G.751, G.752, G.753
and\ G.754\ [10]. This means that digital blocks from a digital multiplex
hierarchy, with a format defined in Rec.\ G.702\ [13] cannot have a designation
taken from this section. They should be designated according to \(sc\ 8.
.PP
\fINote\fR \ \(em\ This section deals with digital transmission only. Analogue
data transmission systems and links are covered by the sections treating
circuits, groups and group links.
.PP
The format of designations of data transmission systems are shown in Table\
7/M.140.
.RT
.ce
\fBH.T. [T7.140]\fR
.ce
TABLE\ 7/M.140
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(24p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | lw(18p) | cw(24p) | cw(18p) .
Format of designation Town A / {
Suffix for transmission station or international exchange
(optional)
} \(em Town B / {
Suffix for transmission station or international exchange
(optional)
} Function code Serial number
_
.T&
cw(24p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
Signs Characters Slash Letters/ digits Hyphen Characters Slash Letters/ digits Space Letters/ digits Digits
_
.T&
cw(24p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
Number of characters \(= 12 1 \(= 3 1 \(= 12 1 \(= 3 1 \(= 5 1\(hy3
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 7/M.140 [T7.140], p.\fR
.sp 1P
.RT
.ad b
.RT
.PP
The elements of the format are as follows:
.LP
a)
\fITraffic relation\fR
.LP
Town A and town B, possibly with a transmission station
or international exchange suffix, represent the two terminal stations of the
data transmission system. The names are arranged in alphabetical order.
For the spelling see \(sc\ 1.1. If the town name exceeds the maximum length
of
12\ characters, the responsible Administration should supply a suitable
abbreviation which must be unique (see \(sc\ 0.1).
.LP
The transmission station or international exchange suffix
(maximum 3\ characters) is an optional field which may be used to further
identify the terminal point when there is more than one carrier operating in
the town. The necessity for a suffix and its form should be decided by the
Administration operating the circuit in the town concerned.
.LP
b)
\fIFunction code\fR
.LP
This code consists of a 2 to 4 digits number which together with a letter
showing the multiplication factor, indicates the bit rate.
.LP
The letters to be used to indicate the multiplication factor are:
.LP
\fIBit rate of system\fR
\fILetter\fR
.LP
Up to 999\ bit/s
B
.LP
\ \ \ \ \ 1\ 000\ to\ 9\ 999\ bit/s
H
.LP
\ \ \ \ 10\ 000\ to\ 9\ 999\ 999\ bit/s
K
.LP
10\ 000\ 000\ to\ 9\ 999\ 999\ 999\ bit/s
M
.bp
.LP
c)
\fISerial number:\fR
.LP
This is a 1 to 3 digit number counting the number of data
transmission systems with the same traffic relation and the same function
code.
.LP
\fINote\fR \ \(em\ The use of the data transmission system (e.g.
multiplex of digital leased circuits, broadcasting, video) will be recorded
in Related Information under item\ 9 (Use, see \(sc\ 12.9.).
.LP
\fIExample\ 1:\fR
.LP
The first 9600 bit/s data transmission system between Lisboa
and New York (for example in use for a multiplex of 2400 bit/s and 7200
bit/s circuits):
.LP
Lisboa\(emNew York 96H1.
.LP
\fIExample\ 2:\fR
.LP
The eleventh 2048 kbit/s data transmission system between
London and Paris (used, for example, for public video conference):
.LP
London\(emParis 2048K11.
.sp 1P
.LP
11.2
\fIData transmission links\fR
.sp 9p
.RT
.PP
Data transmission links are designated as data transmission
systems.
.RT
.sp 1P
.LP
11.3
\fIRelated Information\fR
.sp 9p
.RT
.PP
The additional information on data transmission systems is covered by the
following items:
.RT
.LP
1.
Urgency for restoration;
.LP
2.
Terminal countries;
.LP
3.
Administrations', carriers' or broadcasting companies'
names;
.LP
4.
Control and sub\(hycontrol station(s);
.LP
5.
Fault report points;
.LP
6.
Routing;
.LP
7.
Association;
.LP
8.
Equipment information;
.LP
9.
Use;
.LP
10.
Transmission medium information;
.LP
11.
Composition of transmission;
.LP
12.
(Empty item, use: \*Q\(em;\*U);
.LP
13.
Occupancy;
.PP
The various items will be dealt with in \(sc\ 12.
.sp 2P
.LP
\fB12\fR \fBRelated information for international digital blocks, paths
and data transmission systems\fR
.sp 1P
.RT
.PP
The following sections explain the items of Related Information
concerned with international digital blocks, paths and data transmission
systems. Full examples for the designation information of an international
digital block, an international digital path and an international data
transmission system are given in Annex\ A, \(sc\ A.4.
.RT
.sp 1P
.LP
12.1
\fIUrgency for restoration\fR \fI(item 1)\fR
.sp 9p
.RT
.PP
This item supplies information on the urgency of restoration of the block,
path,\ etc. based upon bilateral agreement between the terminal
Administrations.
.PP
\fIFormat:\fR
.RT
.LP
1.
xx . | | | xx; (maximum 10 characters)
.LP
\fIIllustration:\fR
.LP
a)
If the priority is top: 1;
.LP
If the priority is second: 2;
.LP
If the priority is third: 3; or
.bp
.LP
b)
If repair is required within e.g. 24 hours: \(=\ 24\ h; or
.LP
c)
If no urgency has to be indicated: \(em;
.LP
\fIExample:\fR
.LP
If a block needs top priority in the case of restoration:
.LP
1. 1;
.sp 1P
.LP
12.2
\fITerminal countries\fR \fI(item 2)\fR
.sp 9p
.RT
.PP
This item presents the countries in which the block, path or data transmission
system is terminating.
.PP
\fIFormat:\fR
.RT
.LP
2.
XXX, YYY; (3 characters for each) or 2. XXX;
.LP
\fISpecification:\fR
.LP
XXX:
code for country of town A
.LP
YYY:
code for country of town B
.LP
In the case of multiple destination unidirectional block,
only\ XXX applies.
.LP
\fINote\fR \ \(em\ The codes are according to ISO Standard 3166\ [2].
.LP
\fIExample:\fR
.LP
For a digital block Bruxelles\(emFrankfurt 120N1:
.LP
2.
BEL, DEU;
.sp 1P
.LP
12.3
\fINames of Administration, carriers or broadcasting\fR
\fIcompanies\fR \fI(item 3)\fR
.sp 9p
.RT
.PP
This item records the names of the carriers,\ etc. which operate the block,
path,\ etc.
.PP
\fIFormat:\fR
.RT
.LP
3.
XXXXXX, YYYYYY; (maximum 6 characters for each)
ou 3. XXXXXX;
.LP
\fISpecification:\fR
.LP
XXXXXX:
name of company in town A
.LP
YYYYYY:
name of company in town B
.LP
In the case of a multiple destination unidirectional block,
only\ XXXXXX applies.
.LP
\fIExample:\fR
.LP
For a digital block Frankfurt\(emLondon 30N1 operated by British Telecom
International and Deutsche Bundespost:
.LP
3.
DBP, BTI;
.sp 1P
.LP
12.4
\fIControl station (sub\(hycontrol station(s))\fR \fI(item 4)\fR
.sp 9p
.RT
.PP
This item lists the appointed control station and sub\(hycontrol
stations (according to Recs.\ M.80 and\ M.90). Further details about the
stations can be found in the list of contact points (Rec.\ M.93).
.PP
\fIFormat:\fR
.RT
.LP
4.
CS:
designation of control station,
.LP
SCS1:
designation of sub\(hycontrol station,
.LP
SCS2:
designation of sub\(hycontrol station,
.LP
\ . \ \ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .
.LP
\ . \ \ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .
.LP
\ . \ \ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .
.LP
SCSn:
designation of sub\(hycontrol station,
.LP
or, in the case of a multiple destination unidirectional
block:
.LP
4.
CS:
designation of control station.
.LP
\fISpecification:\fR
.LP
CS:
designation of the control station,
.LP
SCS1:
designation of the terminal sub\(hycontrol
station,
.LP
SCS2\ to\ SCSn:
if applicable: other sub\(hycontrol
stations, are to be placed in the geographical
order according to the traffic relation.
.LP
In the case of a multiple destination unidirectional
block, only CS applies.
.bp
.LP
\fIExample\ 1:\fR
.LP
For the digital block Stockholm\(emVenezia 30N1 with control
station Stockholm and sub\(hycontrol stations Venezia and Paris:
.LP
4.
CS:
Stockholm/HAM;
.LP
SCS1:
Venezia/CEN;
.LP
SCS2:
Paris/ARC;
.LP
\fIExample\ 2:\fR
.LP
For the digital block Rio de Janeiro\(em(MU) 30N1:
.LP
4.
CS:
Rio de Janei/1;
.sp 1P
.LP
12.5
\fIFault report points\fR \fI(item 5)\fR
.sp 9p
.RT
.PP
This item presents the names of both fault report points on the
block, path,\ etc. (according to Rec.\ M.130). Further details about the fault
report points can be found in the list of contact points (Rec.\ M.93).
.PP
\fIFormat:\fR
.RT
.LP
5.
Designation of fault report point, Designation of fault
report point;
.LP
or
.LP
5.
Designation of fault report point;
.LP
\fISpecification:\fR
.LP
The first fault report point is the one of country of town\ A.
.LP
The second fault report point is the one of country of town\ B.
.LP
In the case of a multiple destination unidirectional block, the second
station and the comma are omitted.
.LP
\fIExample\ 1:\fR
.LP
For the digital block Lisboa\(emZuerich 30N1:
.LP
5.
Lisboa/MAR, Zuerich/SEL;
.LP
\fIExample\ 2:\fR
.LP
For the digital block Jakarta\(em(MU) 30N1:
.LP
5.
Jakarta/1;
.sp 1P
.LP
12.6
\fIRouting\fR \fI(item 6)\fR
.sp 9p
.RT
.PP
This item records the next higher block within the multiplex
hierarchy on which the block path, data transmission system, has been routed
and the position number, or in the case of the highest multiplex level, the
transmission media on which the block has been routed.
.PP
\fIFormat:\fR
.RT
.LP
6.
Designation of an international block/position number
or designation of transmission medium, Designation of an international
block/position number or designation of transmission medium,\ . | | ,
Designation of an international block/position number or designation of
transmission
medium;
.LP
\fINote\fR \ \(em\ Two consecutive unidirectional blocks are separated
by a +\ sign instead of a comma.
.LP
\fISpecification:\fR
.LP
The designation of an international block refers to the next
higher level in the digital multiplex hierarchy. If there are more than one,
the blocks are noted in geographical order from town\ A to town\ B.
.LP
The designation of the transmission medium refers to the
transmission medium leaving the country of town\ A and to the transmission
medium entering the country of town\ B respectively.
.LP
As no CCITT designations of transmission media, nor digital
line or radio sections are provided for the time being, the terminal countries
should provide designations or agree on designations.
.LP
If there is only one transmission medium, the designation of
this medium applies.
.LP
\fIExample\ 1:\fR
.LP
For the primary digital block Frankfurt\(emZuerich 30N7:
.LP
6.
Frankfurt\(emZuerich 120N1/3;
.bp
.LP
\fIExample\ 2:\fR
.LP
For the block Bruxelles\(emLondon 1920N1, with transmission
medium corresponding to submarine cable:
.LP
6.
UK\(emB 5;
.sp 1P
.LP
12.7
\fIAssociation\fR \fI(item 7)\fR
.sp 9p
.RT
.PP
This item identifies whether there are associated blocks, paths,
data transmission systems and if so, of which nature.
.PP
\fIFormat:\fR
.RT
.LP
7.
Association code: designation(s) of the associated
block(s), path(s);
.LP
\fISpecification:\fR
.LP
If the block \fIhas\fR | a reserve block the association code is:
S\ followed by the function code and the serial number of the principal block.
.LP
If the block \fIis\fR | a reserve block: the association code is:
function code followed by\ S and the serial number of the reserve block.
.LP
The same applies for digital paths and data transmission
systems.
.LP
\fIExample:\fR
.LP
If the path Hongkong\(emSingapore 30N801 is the restoration path for
the normal block Hongkong\(emSingapore 30N3, the Related Information for
the normal block under Association must show:
.LP
7.
S30N3: Hongkong\(emSingapore 30N801;
.sp 1P
.LP
12.8
\fIEquipment informations\fR \fI(item 8)\fR \v'3p'
.sp 9p
.RT
.LP
12.8.1\ \ This item records information on equipment in the block, path,\ etc.
which requires special maintenance attention.
.LP
\fIFormat:\fR
.LP
8.
XX, XX, XX, XX;
.LP
\fISpecification:\fR
.LP
If the block has been routed via TDMA: TD.
.LP
\fINote\fR \ \(em\ If there is a need to record any additional equipment
information, the next free codeplaces are available for that purpose. The
codes to be used must consist of two characters, be unique and can be chosen
by bilateral agreement between Administrations.
.sp 1P
.LP
12.8.2\ \ For data transmission systems this item supplies information
about the multiplex configuration.
.sp 9p
.RT
.LP
\fIFormat for data transmission systems only\fR :
.LP
8.
XXXXXXYYYYZZZZZ
.LP
\fISpecification:\fR
.LP
XXXXXX
refers to the Recommendation series,
.LP
YYYY
refers to the Recommendation number,
.LP
ZZZZZ
refers to the section, paragraph, table\ etc.,
number.
.LP
\fIExample:\fR
.LP
For a 9600 bit/s data transmission system with a multiplex
configuration as defined in Table\ A\(hy1/M.1320, item\ 8 will present:
.LP
8.
Rec. M.1320TA\(hy1;
.sp 1P
.LP
12.9
\fIUse\fR \fI(item 9)\fR
.sp 9p
.RT
.PP
This item identifies for what purpose the block, path, data
transmission system is used (if this known by the Administration and of use
for maintenance).
.PP
\fIFormat:\fR
.RT
.LP
9.
XXXXXX; (maximum 6 characters)
.bp
.LP
\fISpecification:\fR
.LP
XXXXXX refers to (among others) the designatory letters\ Z, B, D, V,\
etc., to indicate the use of the block. If no information is available,
the sign\ \(em is used.
.LP
\fIExample:\fR
.LP
If the digital block Frankfurt\(emLuxembourg 30N1 is used for
sound\(hyprogramme transmission:
.LP
9.
R;
.sp 1P
.LP
12.10
\fITransmision medium information\fR \fI(item 10)\fR
.sp 9p
.RT
.PP
This item identifies whether a satellite is involved in the
routing.
.PP
\fIFormat:\fR
.RT
.LP
10.
ST; or \(em;
.LP
\fISpecification:\fR
.LP
If the block has been routed via satellite: ST
.LP
If the block has not been routed via satellite: \(em
.LP
\fIExample:\fR
.LP
For the block Paris\(em(MU) 30N1:
.LP
10.
ST;
.sp 2P
.LP
12.11
\fIEnd\(hyto\(hyend information or composition of transmission\fR \fI(item\
11)\fR
.sp 1P
.RT
.sp 1P
.LP
12.11.1
\fIEnd\(hyto\(hyend information (for blocks and paths on mixed\fR
\fIanalogue/digital routes only)\fR
.sp 9p
.RT
.PP
This item provides information on the destinations of the traffic carried
by the block or path.
.PP
\fIFormat:\fR
.RT
.LP
11.
X . | | X, Y . | | Y; (maximum 12 characters each)
or\ \(em;
.LP
\fISpecification:\fR
.LP
X . | | X and Y . | | Y are the names of a town and refer to
the destinations of the traffic on the block/path. The destinations are
placed according to the order of towns in the traffic relation.
.LP
If the block has multiple destination the town name is replaced by the
code:\ M.
.LP
If the block is within a digital environment X . | | X, Y . | | Y
is replaced by the sign\ \(em.
.LP
\fIExample\ 1:\fR
.LP
For primary digital block Frankfurt\(emParis 30NC6 carrying from Frankfurt\(emLondon:
.LP
11.
Frankfurt, London;
.LP
\fIExample\ 2:\fR
.LP
For primary block Amsterdam\(emBruxelles 30NC146 carrying
traffic from London to Luxembourg:
.LP
11.
London, Luxembourg;
.sp 1P
.LP
12.11.2
\fIComposition of transmission (for data transmission systems)\fR
.sp 9p
.RT
.PP
This item shows the type of transmission on the data transmission system.
.PP
\fIFormat:\fR
.RT
.LP
11.
A; N; or C;
.LP
\fISpecification:\fR
.LP
If the transmission is analogue: A
.LP
If the transmission is digital: N
.LP
If the transmission is mixed analogue/digital: C
.bp
.sp 1P
.LP
12.12
\fIBit rate\fR \fI(for blocks and paths) (item 12)\fR
.sp 9p
.RT
.PP
This item shows the bit rate of the block or path.
.PP
\fIFormat:\fR
.RT
.LP
12.
xxxx.x kbit/s or Mbit/s;
.LP
Rules for the notation of the bit rate figures:
.LP
Leading zeros may be omitted and if the decimal is a zero, this decimal
and the decimal sign may also be omitted.
.LP
If the figure is up to 9 999 999, use kbit/s.
.LP
If the figure is 10 000 000 or more, use Mbit/s.
.LP
\fINote\fR \ \(em\ For data transmission systems, use the sign\ \(em.
.LP
\fIExample\ 1:\fR
.LP
For the digital block New York\(emTokyo 24N2:
.LP
12.
1544 kbit/s;
.LP
\fIExample\ 2:\fR
.LP
For the digital block Bruxelles\(emLuxembourg 480N1:
.LP
12.
34 Mbit/s;
.sp 1P
.LP
12.13
\fIOccupancy\fR \fI(for blocks and for data transmission\fR
\fIsystems) (item\ 13)\fR
.sp 9p
.RT
.PP
This item lists the occupancy of the block expressed by the next
lower blocks and/or circuits and/or data transmission systems which have
been routed in the block.
.PP
\fIFormat in the case of a primary block:\fR
.RT
.LP
(The same format applies to data transmission systems,
replacing \*Qtime slot number\*U by \*Qchannel number\*U according to
Recommendation\ M.1320\ [14]).
.LP
\ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .
.LP
\ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .
.LP
\ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .\ \ \ \ .
.LP
Time slot number: designation of the circuit, or the
sign\ \(em;
.LP
\fIFormat in the case of a secondary or higher level block:\fR
.LP
13.
Position number: designation of a block, of a leased
circuit, of a data transmission system or the
sign\ \(em,
.LP
\ \ .\ \ \ \ .\ \ \ \ .
.LP
\ \ .\ \ \ \ .\ \ \ \ .
.LP
\ \ .\ \ \ \ .\ \ \ \ .
.LP
Position number: designation of a block, of a leased
circuit, of a data transmission system or the
sign\ \(em,
.LP
\fISpecification:\fR
.LP
If the position number is occupied by a next lower digital
block: designation of this block.
.LP
If the position number is occupied by a digital leased circuit (with
a bit rate corresponding to the bit rate of the next lower multiplex
level): designation of this leased circuit.
.LP
If the position number is occupied by a data transmission
system (with a bit rate corresponding to the bit rate of the next lower
multiplex level): designation of this data transmission system.
.LP
If the position number is not in use: the sign\ \(em.
.LP
\fIExample\ 1:\fR
.LP
For the digital block Geneve\(emParis 120N2:
.LP
13.
01:
Geneve\(emLisboa 30N1,
.LP
02:
\(em,
.LP
03:
Geneve\(emParis 2048K1,
.LP
04:
Bruxelles\(emWien 30N1;
.bp
.LP
\fIExample\ 2:\fR
.LP
For the digital block New York\(emParis 24N5:
.LP
13.
01:
New York/24\(emParis/PT2 Z1,
.LP
02:
New York/24\(emParis/PT2 Z3,
.LP
03:
New York/24\(emParis/PT2 Z5,
.LP
04:
Paris/PT2\(emNew York/24 Z2,
.LP
05:
Paris/PT2\(emNew York/24 Z4,
.LP
06:
Paris/PT2\(emNew York/24 Z6,
.LP
07:
\(em,
.LP
08:
\(em,
.LP
09:
\(em,
.LP
10:
Orlando/TS1\(emToulouse/FER 64K1,
.LP
11:
\(em,
.LP
12:
\(em,
.LP
13:
\(em,
.LP
14:
\(em,
.LP
15:
New York/TS1\(emParis/ARC R1,
.LP
16:
New York/TS1\(emParis/ARC R3,
.LP
17:
\(em,
.LP
18:
\(em,
.LP
19:
\(em,
.LP
20:
Paris/BEA\(emWashington/TS1 NP1,
.LP
21:
\(em,
.LP
22:
\(em,
.LP
23:
\(em,
.LP
24:
\(em,
.sp 1P
.LP
12.14
\fIActual number of channels\fR \fI(primary blocks only)\fR
\fI(item\ 14)\fR
.sp 9p
.RT
.PP
This item contains the actual number of channels on a primary
digital block.
.PP
\fIFormat:\fR
.RT
.LP
14.
xxx;
.LP
\fISpecification:\fR
.LP
xxx indicates the actual number of channels.
.LP
For higher blocks xxx is replaced by the sign\ \(em.
.LP
\fIExample\ 1:\fR
.LP
For the digital block New York\(emParis 30N5 dedicated to leased circuits:
.LP
14.
31;
.LP
\fIExample\ 2:\fR
.LP
For the digital block London\(emNew York 30N3 used for switched
public telephone circuits with ADPCM, the information may be:
.LP
14.
60;
.LP
\fIExample\ 3:\fR
.LP
For the digital block Honolulu\(emOsaka 24N2 used for switched
public telephone circuits:
.LP
14.
24;
.sp 1P
.LP
12.15
\fIClocking information\fR \fI(for blocks only) (item 15)\fR
.sp 9p
.RT
.PP
This item specifies whether Administrations apply a clocking
system according to Rec.\ G.811\ [15] or use a master/slave system.
.PP
\fIFormat:\fR
.RT
.LP
15
XX . | | XX; (maximum 30 characters)
.bp
.LP
\fISpecification:\fR
.LP
If clocking according to Rec. G.811 is applied: Rec. G.811;
.LP
If a master/slave clocking is applied:
.LP
M = XX . | | XX,
S = XX . | | XX;
.LP
(Town name for the master)
(Town name for the slave)
.LP
\fIExample\ 1:\fR
.LP
Clocking according to Rec. G.811:
.LP
15.
Rec. G.811;
.LP
\fIExample\ 2:\fR
.LP
Clocking according to Master/Slave system:
.LP
15.
M = London, S = Frankfurt;
.sp 1P
.LP
12.16
\fIDirection of transmission\fR \fI(for unidirectional blocks)\fR \fI(item
16)\fR
.sp 9p
.RT
.PP
This item gives information on the direction of transmission of a unidirectional
digital block.
.PP
\fIFormat:\fR
.RT
.LP
16.
I; or A;
.LP
\fISpecification:\fR
.LP
If the block is unidirectional and if it has a single
destination:
.LP
\(em
if the direction of transmission is in alphabetical
order\ A;
.LP
\(em
if the direction of transmission is in inverse
alphabetical order\ I;
.LP
\fIExample:\fR
.LP
For the unidirectional digital block London\(hyRoma 30N1
transmitting in the direction Roma to London:
.LP
16.
I;
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation M.140)
.sp 9p
.RT
.ce 0
.ce 1000
\fBFull examples for designation information\fR
.sp 1P
.RT
.ce 0
.LP
A.1
\fIFull example for the designation information of a public switched\fR
\fItelephone circuit\fR
.sp 1P
.RT
.PP
The circuit is the 604th both\(hyway telephone circuit between Sherman
Oaks\ 4ES and Tokyo Shinjuku, operated by AT&T and KDD. The signalling
type
is CCITT No.\ 6 with band/circuit number assigned as\ 000/03. The control
station and sub\(hycontrol station of the circuit are Sherman Oaks\(hytransmission
station\ 1 and Tokyo\(hytransmission station\ 1 respectively. Both stations
are also the fault report points of the circuit. The circuit has been routed
on the 4th channel of the first group between Sherman Oaks and Ibaraki
which is routed via satellite and has been connected to digital blocks
in domestic networks.
.PP
\fIDesignation:\fR
.RT
.LP
Sherman Oaks/4ES\(emTokyo/SJK B604
.LP
\fIRelated Information:\fR
.LP
1.
2;
.LP
2.
USA, JPN;
.LP
3.
ATT, KDD;
.LP
4.
CS: Sherman Oaks/TS1,
.LP
SCS1: Tokyo/TS1;
.LP
5.
Sherman Oaks/TS1, Tokyo/TS1;
.LP
6.
Ibaraki\(emSherman Oaks 12CO1/4;
.LP
7.
\(em;
.bp
.LP
8.
\(em;
.LP
9.
\(em;
.LP
10.
ST;
.LP
11.
C;
.LP
12.
3.4 kHz;
.LP
13.
C6, 000/03.
.sp 1P
.LP
A.2
\fIFull example for the designation information of a leased analogue\fR
\fIcircuit\fR
.sp 9p
.RT
.PP
The circuit is the first analogue leased circuit used for data
transmission between London and Frankfurt, operated by British Telecom
International and the Deutsche Bundespost. The signalling type is
500\ Hz/20\ Hz. The control station and sub\(hycontrol station of the circuit
are
London Mollison and Frankfurt\ 0 respectively. Both stations are also the
fault report points of the circuit. The circuit is routed on the 3rd channel
of the first group between Frankfurt and London. As regards the parameters
of the
circuit, Recommendation\ M.1020\ [9] is applied. The maintenance contract
between Administrations and customer is repair within 24\ hours.
.PP
\fIDesignation:\fR
.RT
.LP
Frankfurt\(emLondon DP1.
.LP
\fIRelated Information:\fR
.LP
1.
\(= 24 h;
.LP
2.
DEU, GBR;
.LP
3.
DBP, BTI;
.LP
4.
CS: London/SM,
.LP
SCS1: Frankfurt/0;
.LP
5.
Frankfurt/0, London/SM;
.LP
6.
Frankfurt\(emLondon 1201/3;
.LP
7.
\(em;
.LP
8.
\(em;
.LP
9.
D;
.LP
10.
\(em;
.LP
11.
A;
.LP
12.
3.4 kHz;
.LP
13.
500/20;
.LP
14.
Rec. M.1020.
.sp 2P
.LP
A.3
\fIFull examples for the designation information of an international\fR
\fIgroup and an international group links\fR
.sp 1P
.RT
.sp 1P
.LP
A.3.1
\fIFull example for the designation information of an international\fR
\fIgroup\fR
.sp 9p
.RT
.PP
\fINote\fR \ \(em\ The numbers between parentheses refer to the numbers of
the items in the Related Information.
.PP
The international group is the fifth group between Amsterdam and
Paris. The urgency for restoration (1) is 3rd priority, the terminal countries
(2) are Netherlands and France, the Administrations involved (3) are
Netherlands PTT and France Telecom, the control station and sub\(hycontrol
station (4) are Paris Archives and Amsterdam\ 1 respectively, the fault
report points
(5) are Amsterdam\ 2 and Paris Archives, the routing (6) of the group is
in the supergroup Amsterdam\(emBruxelles\ 6011 on position\ 1 and in the
supergroup
Bruxelles\(emParis\ 6002 on position\ 3, there is an associated group (7)
carrying traffic but indicated for restoration namely
Amsterdam\(emParis\ 1209, there is special equipment involved (8) because
the group is carrying companded
circuits, the use (9) is: Z\(hycircuits and a DP circuit, no satellite (10) is
involved, no end\(hyto\(hyend information (11) is to be recorded, the bandwith
(12) is 48\ kHz and the occupancy (13) is to be seen from the example.
.PP
\fIDesignation:\fR
.RT
.LP
Amsterdam\(emParis 1205
.bp
.LP
\fIRelated Information:\fR
.LP
1.
3;
.LP
2.
NLD, FRA;
.LP
3.
NLDPTT, FRATEL;
.LP
4.
CS: Paris/ARC,
.LP
SCS1: Amsterdam/1;
.LP
5.
Amsterdam/2, Paris/ARC;
.LP
6.
Amsterdam\(emBruxelles 6011/1,
.LP
Bruxelles\(emParis 6002/3;
.LP
7.
S1205: Amsterdam\(emParis 1209;
.LP
8.
CO;
.LP
9.
Z, DP;
.LP
10.
\(em;
.LP
11.
\(em;
.LP
12.
48 kHz;
.LP
13.
01:
Amsterdam\(emParis Z111,
.LP
02:
Amsterdam\(emParis Z113,
.LP
03:
Amsterdam\(emParis Z115,
.LP
04:
Amsterdam\(emParis Z117,
.LP
05:
Amsterdam\(emParis Z119,
.LP
06:
Amsterdam\(emParis Z121,
.LP
07:
Paris\(emAmsterdam Z120,
.LP
08:
Paris\(emAmsterdam Z122,
.LP
09:
Paris\(emAmsterdam Z124,
.LP
10:
Paris\(emAmsterdam Z126,
.LP
11:
Paris\(emAmsterdam Z128,
.LP
12:
Amsterdam\(emParis DP5,
.sp 1P
.LP
A.3.2
\fIFull example for the designation information of an international\fR
\fIgroup link\fR
.sp 9p
.RT
.PP
\fINote\fR \ \(em\ The numbers between parentheses refer to the numbers of
the items in the Related Information.
.PP
The link is the first restoration group link between Paris and Geneve.
The urgency for restoration (1) is 3rd priority, the terminal countries
(2) are Switzerland and France, the Administrations (3) are Swiss PTT and
France
Telecom, the control and sub\(hycontrol stations (4) are Geneve Monthoux
and Paris Archives respectively, the fault report points (5) are the same
stations, the routing (6) is in the second supergroup between Geneve and
Annemasse on
position\ 1, there is no information to be recorded about association (7),
special equipment (8), use (9), there is no satellite involved (10), no
end\(hyto\(hyend information (11) is required, the bandwith (12) is 48\ kHz.
.PP
\fIDesignation:\fR
.RT
.LP
Geneve\(emParis 12801
.LP
\fIRelated Information:\fR
.LP
1.
3;
.LP
2.
CHE, FRA;
.LP
3.
CHEPTT, FRATEL;
.LP
4.
CS: Geneve/MON,
.LP
SCS1: Paris/ARC;
.LP
5.
Geneve/MON, Paris/ARC;
.LP
6.
Annemasse\(emGeneve 6002/1;
.LP
7.
\(em;
.LP
8.
\(em;
.LP
9.
\(em;
.LP
10.
\(em;
.LP
11.
\(em;
.LP
12.
48 kHz;
.bp
.sp 2P
.LP
A.4
\fIFull examples for the designation information of an international\fR
\fIdigital block, digital path and data transmission system\fR
.sp 1P
.RT
.sp 1P
.LP
A.4.1
\fIFull examle for the designation information of an international\fR
\fIdigital block\fR
.sp 9p
.RT
.PP
\fINote\fR \ \(em\ The numbers between parentheses refer to the numbers of
the items in the Related Information.
.PP
The international digital block is the 12th primary digital block
between Roma and Paris. The urgency for restoration (1) is 2, the terminal
countries (2) are France and Italy, the Administrations involved (3) are
France Telecom and ASST, control station (4) is Roma\ 1 and sub\(hycontrol
station is Paris Archives, the fault report points (5) are the same stations,
the block has been routed (6) in the secondary digital block Paris\(emRoma\
120N2 on
position
.PP
number\ 3, it has an associated block (7) indicated for restoration: Paris\(emRoma
30N5, no special equipment (8) is involved, the use of the block (9) is
DP\(hy and NP\(hycircuits, no satellite is involved (10), no end\(hyto\(hyend
information (11) is required, the bit rate (12) is 2.048\ Mbit/s, the occupancy
(13) is seen in the example, the actual number of channels (14) is\ 31,
the clocking system (15) is a master/slave system with the master in Paris
and the slave in Roma.
.PP
\fIDesignation:\fR
.RT
.LP
Paris\(emRoma 30N12
.LP
\fIRelated Information:\fR
.LP
1.
2;
.LP
2.
FRA, ITA;
.LP
3.
FRATEL, ASST;
.LP
4.
CS: Roma/1,
.LP
SCS1: Paris/ARC;
.LP
5.
Paris/ARC, Roma/1;
.LP
6.
Paris\(emRoma 120N2/3;
.LP
7.
S30N12: Paris\(emRoma 30N5;
.LP
8.
\(em;
.LP
9.
DP, NP;
.LP
10.
\(em;
.LP
11.
\(em;
.LP
12.
2048 kbit/s;
.LP
13.
01:
London\(emRoma DP12,
.LP
02:
Paris\(emRoma DP2,
.LP
03:
Napoli\(emRouen NP1,
.LP
04:
Paris\(emRoma NP3,
.LP
05:
Paris\(emRoma NP4,
.LP
06:
Paris\(emRoma NP5,
.LP
07:
\(em,
.LP
08:
\(em,
.LP
09:
\(em,
.LP
10:
Lille\(emRoma DP1,
.LP
11:
Paris\(emRoma DP5,
.LP
12:
\(em,
.LP
13:
\(em,
.LP
14:
\(em,
.LP
15:
\(em,
.LP
16:
Bruxelles\(emRoma DPM4,
.LP
17:
Paris\(emRoma NPM1,
.LP
18:
\(em,
.LP
19:
\(em,
.LP
20:
\(em,
.LP
21:
\(em,
.LP
22:
\(em,
.LP
23:
\(em,
.bp
.LP
24:
\(em,
.LP
25:
\(em,
.LP
26:
\(em,
.LP
27:
\(em,
.LP
28:
\(em,
.LP
29:
\(em,
.LP
30:
\(em,
.LP
31:
\(em;
.LP
14.
31;
.LP
15.
M = Paris, S = Roma;
.sp 1P
.LP
A.4.2
\fIFull example for the designation information of an international\fR
\fIdigital path\fR
.sp 9p
.RT
.PP
\fINote\fR \ \(em\ The numbers between parentheses refer to the numbers of
the items in the Related Information.
.PP
The international digital path is the first restoration digital second
order path between Paris and Bruxelles. The urgency for restoration (1)
is\ 3, the terminal countries (2) are Belgium and France, the Administrations
involved (3) are the Belgium RTT and France Telecom, control station (4)
is Bruxelles
BLA and sub\(hycontrol station is Paris Archives, the fault report points
(5) are the same stations, the path has been routed (6) in the first third
order block Bruxelles\(emParis on position number\ 1, there are no associated
blocks (7), no
special equipment (8), use (9) has not been indicated, no satellite is
involved (10), no end\(hyto\(hyend information (11) is required, the bit
rate (12) is
8.448\ Mbit/s.
.PP
\fIDesignations:\fR
.RT
.LP
Bruxelles\(emParis 120N801
.LP
\fIRelated Information:\fR
.LP
1.
3;
.LP
2.
BEL, FRA;
.LP
3.
BELRTT, FRATEL;
.LP
4.
CS: Bruxelles/BLA,
.LP
SCS1: Paris/ARC;
.LP
5.
Bruxelles/BLA, Paris/ARC;
.LP
6.
Bruxelles\(emParis 480N1/1;
.LP
7.
\(em;
.LP
8.
\(em;
.LP
9.
\(em;
.LP
10.
\(em;
.LP
11.
\(em;
.LP
12.
8448 kbit/s;
.sp 1P
.LP
A.4.3
\fIFull example for the designation information of an international\fR
\fIdata transmission system\fR
.sp 9p
.RT
.PP
\fINote\fR \ \(em\ The numbers between parentheses refer to the numbers of
the items in the Related Information.
.PP
The international data transmission system is the first 64 kbit/s data
transmission system between London and Paris. The urgency for restoration
(1) is\ 1, the terminal countries (2) are United Kingdom and France, the
Administrations involved (3) are British Telecom International and France
.PP
Telecom, the control and sub\(hycontrol stations (4) are London Mollison and
Paris Archives respectively, the fault report points (5) are the same stations,
the system has been routed (6) in the 12th primary block between Paris
and
London on timeslot number\ 3, there is no information to be recorded about
association (7), equipment information (8) and use (9), there is no satellite
involved (10), composition of transmission (11), is digital, item (12)
does not apply, the occupancy (13) is seen in the example.
.PP
\fIDesignation:\fR
.RT
.LP
London\(emParis 64K1
.LP
\fIRelated Information:\fR
.LP
1.
1;
.LP
2.
GBR, FRA;
.LP
3.
BTI, FRATEL;
.bp
.LP
4.
CS: London/SM,
.LP
SCS1: Paris/ARC;
.LP
5.
London/SM, Paris/ARC;
.LP
6.
London\(emParis 30N12/3;
.LP
7.
\(em;
.LP
8.
\(em;
.LP
9.
\(em;
.LP
10.
\(em;
.LP
11.
N;
.LP
12.
\(em;
.LP
13.
A4:
London\(emParis NP12,
.LP
B4:
London\(emToulouse NP3,
.LP
C4:
\(em;
.LP
D4:
Dublin\(emParis NP6,
.LP
E4:
London\(emParis NP11,
.LP
F4:
London\(emParis NP14;
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(to Recommendation M.140)
.sp 9p
.RT
.ce 0
.ce 1000
\fBReference section numbers for the various types of routes\fR
.sp 1P
.RT
.ce 0
.LP
\fISection\fR \fIType of international route\fR
.sp 1P
.RT
.sp 1P
.LP
1.2.2
Telephone circuits used in manual operation
.sp 9p
.RT
.LP
1.2.3
One\(hyway telephone circuits used for semi\(hyautomatic or automatic
operation
.LP
1.2.4
Both\(hyway telephone circuits used for semi\(hyautomatic or automatic
operation
.LP
1.3
Circuits used for switched telex and telegraph service
.LP
1.4
Circuits in the international public switched data network
.LP
3.2.2
Analogue leased circuit used for telephony
.LP
3.2.3.1
Analogue circuits used for voice\(hyfrequency telegraphy
.LP
3.2.3.2
Analogue leased circuits used for TDM\(hytelegraphy
.LP
3.2.4
Leased telegraph circuits
.LP
3.2.5
Analogue leased circuits used for data transmission
.LP
3.2.6
Analogue leased circuits used for phototelegraphy or facsimile
.LP
3.2.7.1
Analogue leased unidirectional sound\(hyprogramme transmission
circuits
.LP
3.2.7.2
Analogue leased reversible sound\(hyprogramme transmission circuits
.LP
3.2.8.1
Analogue leased unidirectional television\(hyprogramme circuits
.LP
3.2.8.2
Analogue leased reversible television\(hyprogramme circuits
.LP
3.2.9
Leased circuits used for digital video transmission
.LP
3.2.10
Analogue leased circuits connecting circuit multiplication terminal equipment
at renters' premises
.LP
3.2.11
Analogue leased circuits used for combinations of
transmissions,\ etc.
.LP
3.2.12
Analogue leased circuits connecting three or more locations
.LP
3.2.13
Leased analogue groups, supergroups, etc.
.LP
3.2.14
Leased analogue group, supergroup links
.LP
3.2.15
Digital leased circuits connecting two locations
.LP
3.2.16
Digital leased circuits connecting three or more locations
.bp
.LP
3.3.2.1
Public circuits used for unidirectional sound\(hyprogramme
transmission
.LP
3.3.2.2
Public circuits used for reversible sound\(hyprogramme transmission
.LP
3.3.2.3
Public circuits used for narrow\(hyband sound\(hyprogramme transmission
.LP
3.3.3.1
Public circuits used for unidirectional television transmission
.LP
3.3.3.2
Public circuits used for reversible television transmission
.LP
3.3.4
Public circuits for digital audio and video transmission
.LP
3.3.5
Public telephone\(hytype circuits used for phototelegraphy or facsimile
.LP
3.3.6
Telephone\(hytype circuits used to provide voice\(hyfrequency telegraph
links
.LP
3.3.7
Telephone\(hytype circuits used to provide time division multiplex
telegraph systems
.LP
3.3.8
Telephone\(hytype circuits used for data transmission
.LP
3.3.9
Telephone\(hytype circuits used as transfer links for common channel
Signalling Systems Nos.\ 6 and\ 7
.LP
5.2.1
Groups (bidirectional)
.LP
5.2.2
Supergroups (bidirectional)
.LP
5.2.3
Mastergroups (bidirectional)
.LP
5.2.4
Supermastergroup (bidirectional)
.LP
5.2.6
Restoration groups and supergroups (bidirectional)
.LP
5.3.1
Multiple destination unidirectional groups and supergroups
.LP
5.3.2
Single destination unidirectional groups and supergroups
.LP
6.1.1
Conventional group and supergroup links
.LP
6.1.2
Restoration links
.LP
6.2
Line links
.LP
8.2
Bidirectional digital blocks
.LP
8.3
Restoration digital blocks
.LP
8.4
Multiple destination unidirectional digital blocks
.LP
8.5
Single destination unidirectional digital blocks
.LP
9.1
Conventional digital paths
.LP
9.2
Restoration digital paths
.LP
10.1.1
Groups and supergroups, etc. on a mixed analogue/digital route
.LP
10.1.2
Digital blocks and paths on a mixed analogue/digital route
.LP
10.2
Routes with two analogue\(hyto\(hydigital conversions
.LP
11.1
Data transmisssion systems
.LP
11.2
Data transmission links
.sp 2P
.LP
\fBReferences\fR
.sp 1P
.RT
.LP
[1]
CCITT Recommendation \fITerms and definitions of traffic engineering\fR ,
Vol.\ II, Rec.\ E.600.
.LP
[2]
ISO International standard 3166 \fICodes for the representation of names\fR
\fIof countries\fR , Second edition,\ 1981.
.LP
[3]
CCITT Recommendation \fIDesignation of international telegraph circuits\fR
, Vol.\ VI, Rec.\ R.70.
.LP
[4]
CCITT Recommendation \fILining up an international miltiterminal leased\fR
\fIcircuit\fR , Vol.\ IV, Rec.\ M.1055.
.LP
[5]
CCITT Recommendation \fICircuit control station for leased and special\fR
\fIcircuits\fR , Vol.\ IV, Rec.\ M.1012.
.LP
[6]
CCITT Recommendation \fISub\(hycontrol station for leased and special\fR
\fIcircuits\fR , Vol.\ IV, Rec.\ M.1013.
.LP
[7]
CCITT Recommendation \fIPreliminary exchange of information for the\fR
\fIprovision of international leased circuits\fR , Vol.\ IV, Rec.\ M.1045.
.bp
.LP
[8]
CCITT Recommendation \fISignalling systems to be used for international\fR
\fInormal and automatic working on analog leased circuits\fR , Vol.\ VI,
Rec.\ Q.8.
.LP
[9]
CCITT Recommendation \fICharacteristics of special quality international\fR
\fIleased circuits with special bandwidth conditioning\fR , Vol.\ IV, Rec.\
M.1020.
.LP
[10]
CCITT Recommendations concerning the \fISpecification of primary,\fR
\fIsecondary and higher order digital multiplex equipment\fR , Vol.\ III,
Rec.\ G.731 to\ G.755.
.LP
[11]
CCITT Recommendation \fITransmission impairments\fR , Vol.\ III, Rec.\ G.113.
.LP
[12]
CCITT Recommendation \fIInternational telephone routing plan\fR , Vol.\
II, Rec.\ E.171.
.LP
[13]
CCITT Recommendation \fIDigital hierarchy bit rates\fR , Vol.\ III,
Rec.\ G.702.
.LP
[14]
CCITT Recommendation \fINumbering of channels in data transmission\fR
\fIsystems\fR , Vol.\ IV, Rec.\ M.1320.
.LP
[15]
CCITT Recommendation \fITiming requirements at the outputs of reference\fR
\fIclocks and network nodes suitable for plesiochronous operation of\fR
\fIinternational digital links\fR , Vol.\ III, Rec.\ G.811.
.sp 2P
.LP
\fBRecommendation\ M.160\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBSTABILITY\ OF\ TRANSMISSION\fR
.FS
Recommendation\ G.214\ [4] also concerns the subject of the stability of
transmission.
.FE
.EF '% Fascicle\ IV.1\ \(em\ Rec.\ M.160''
.OF '''Fascicle\ IV.1\ \(em\ Rec.\ M.160 %'
.ce 0
.sp 1P
.LP
\fB1\fR \fBVariation of circuit overall loss with time\fR
.FS
See\ [1]
concerning questions of statistical theory.
.FE
.sp 1P
.RT
.PP
1.1
The objective is that the following values should not be
exceeded:
.sp 9p
.RT
.PP
1.1.1
difference between the mean value and the nominal value of the overall
transmission loss:
.PP
0.5\ dB for all circuits,
.PP
1.1.2
standard deviation about the mean value of the variation of the
overall transmission loss:
.PP
1.0\ dB for all circuits.
.PP
However, in the case of circuits which are set up, wholly or in
part, on older type equipment, and which are composed of two or more circuit
sections, a standard deviation not exceeding 1.5\ dB may be admitted.
.RT
.PP
1.2
The method for achieving the above objective values is left to the discretion
of Administrations (better maintenance, fitting of automatic
regulators, etc.).
.sp 9p
.RT
.sp 2P
.LP
\fB2\fR \fBVariation of pilot levels with time on group, supergroup, etc.
links\fR
.sp 1P
.RT
.PP
2.1
The objective is that the following values of M and S should be met, where
M represents the mean deviation of the pilot level from its nominal value
and S represents the standard deviation of the variations of the pilot
level:
.sp 9p
.RT
.PP
2.2
conditions concerning through\(hyconnection points of group,
supergroup, etc. links:
.sp 9p
.RT
.sp 1P
.ce 1000
| | \(=\ 0.5\ dB,\ \ S\ \(=\ 1.3\ dB
.ce 0
.sp 1P
.PP
2.3
conditions concerning the receiving end:
.sp 9p
.RT
.PP
2.3.1
group links:
.sp 1P
.ce 1000
| | \(=\ 0.3\ dB,\ \ S\ \(=\ 0.6\ dB
.ce 0
.sp 1P
.PP
2.3.2
supergroup links:
.LP
| | \(=\ 0.3\ dB,\ \ S\ \(=\ 0.5\ dB
.bp
.sp 1P
.ce 1000
.ce 0
.sp 1P
.PP
2.3.3
mastergroup links:
.sp 1P
.ce 1000
| | \(=\ 0.3\ dB,\ \ S\ \(=\ 0.4\ dB
.ce 0
.sp 1P
.PP
2.3.4
supermastergroup links:
.sp 1P
.ce 1000
| | \(=\ 0.3\ dB,\ \ S\ \(=\ 0.3\ dB.
.ce 0
.sp 1P
.sp 2P
.LP
\fB3\fR \fBPractical application of limits\fR
.sp 1P
.RT
.PP
The assumption is made that the limits set out in \(sc\(sc\ 1 and\ 2 above
for the variation with time of:
.RT
.LP
\(em
the loss of each individual circuit, or
.LP
\(em
the level of each individual group, supergroup, etc.
pilot,
.LP
may be used as limits for the results of measurements made on a set of
circuits, groups, supergroups, etc. at a given time. Experience indicates
that such a use has a practical validity and hence Administrations are
encouraged to use this Recommendation as giving currently practical limits
for sets of
circuits, groups, supergroups, etc. This does not preclude the application
of these limits to single circuits, groups, supergroups,\ etc.
.sp 2P
.LP
\fB4\fR \fBReline\(hyup of circuits, groups, supergroups, etc.\fR
.sp 1P
.RT
.PP
When a circuit, group, supergroup, etc., has its routing or
composition permanently changed over part or all of its length, it is essential
to ensure that a complete line\(hyup of the circuit, group, etc., is made
in
accordance with the relevant line\(hyup Recommendations since the rerouting
constitutes a re\(hyestablishment of the circuit, group, etc.
.PP
This procedure is necessary in order to maintain the transmission
performance and stability of the network. The pressing needs of the
operating services should not be allowed to prevent these measurements from
being properly carried out, since this could only result in a degradation of
the stability and performance of the circuits in the network. Under all
circumstances the circuit control station should be kept advised.
.RT
.sp 2P
.LP
\fB5\fR \fBBasic factors for transmission stability\fR
.sp 1P
.RT
.PP
The CCITT recommends that the following basic factors should be
taken into account for achieving a stable network:
.RT
.sp 1P
.LP
5.1
\fIStaff training\fR
.sp 9p
.RT
.PP
The importance of this factor cannot be overemphasized.
.PP
The staff should understand why level variations are to be kept to a low
value and should be made fully aware of the results of incorrect
adjustments. It is important that adjustments should be made only when
absolutely necessary and an adjustment should never be made to cover up a
fault.
.PP
The staff must realize the possible effects of a brief interruption on
any type of circuit.
.RT
.sp 1P
.LP
5.2
\fIDesign of installations\fR
.sp 9p
.RT
.PP
Installations should be such that sudden interruptions are avoided. For
example, this may be achieved by:
.RT
.LP
a)
the arrangement of transmission equipment to facilitate
maintenance, patching out, the replacement of subassemblies;
.LP
b)
the design of carrier generators with a view to great
reliability;
.LP
c)
the design of power supplies; attention is particularly
drawn to the importance of the judicious choice and grading of
protective devices (fuses, circuit\(hybreakers) in the power
feeds to repeater station racks.
.PP
\fINote\fR \ \(em\ See in this connection Recommendation\ G.231\ [2].
.sp 1P
.LP
5.3
\fICare in the organization of work in international exchanges,\fR
\fIrepeater stations, and on the transmission lines, cables and systems
used in\fR \fIthe international network\fR
.sp 9p
.RT
.PP
Experience has shown that operations carried out on exchange and
repeater station equipment and on the external plants (underground cables,
etc.) are a major cause of attenuation and phase variations and of
interruptions to service in the international network.
.bp
.PP
All work liable to cause interference should therefore be carried out,
when possible, at times of light traffic. It must be recognized that for
very long routes it will become increasingly difficult to find suitable
periods of light traffic, bearing in mind the time differences which will
exist between
the terminal countries on such routes. This will require good coordination
and cooperation between Administrations. In particular, the control stations
should be consulted well in advance (see Recommendation\ M.490).
.RT
.sp 1P
.LP
5.4
\fICare in the organization of maintenance\fR
.sp 9p
.RT
.PP
The same reasons for transferring working operations to times of
light traffic apply to maintenance operations.
.PP
It is desirable to avoid all equipment changeovers which are not
absolutely necessary.
.PP
It is also desirable to guard against maintenance operations which
appear harmless but which may, however, result in short interruptions and
which are all the more dangerous if they affect common units (e.g.\ changeover
of
master oscillators).
.RT
.sp 1P
.LP
5.5
\fIPower supplies\fR \v'3p'
.sp 9p
.RT
.PP
5.5.1
Too frequent changeover of power supplies for routine
maintenance must be avoided. It should be possible to make partial tests to
check that the standby motor\(hygenerator starts, without changing over
the power supplies.
.PP
5.5.2
The instruction or training of staff during the day on working
power supplies should be forbidden.
.PP
5.5.3
Changeover of power supplies should be carried out at times of
light traffic and as far as possible at night.
.PP
5.5.4
To ensure that circuits in the international network are not
interrupted owing to the failure of public power supplies, repeater stations
in the international network should have power\(hycontinuity arrangements
which
ensure that the transmission equipment continues to operate, \fIwithout any\fR
\fIinterruption\fR , in the event of a failure of the public power supply.
.sp 1P
.LP
5.6
\fICare in the testing of new equipment\fR
.sp 9p
.RT
.PP
Equipment should not be put into service until after the most
thorough inspection. It is necessary to ensure that the pressing needs
of the operating services do not result in these tests being omitted or
hastily done.
.PP
Where the urgent requirements of the operating services resulted in
equipment being put into service before it had been sufficiently tested, the
equipment should be temporarily taken out of service and a thorough inspection
made as soon as possible.
.RT
.sp 1P
.LP
5.7
\fIVibration testing\fR
.sp 9p
.RT
.PP
Vibration tests, using the principles described in [3], help in
improving transmission stability and in ensuring satisfactory operation of
transmission equipment. They should be made, wherever applicable, when new
equipment is put into service, under special circumstances for fault locating
purposes or even as a routine measure for preventive maintenance, if the
Administration concerned deems it necessary.
.RT
.sp 1P
.LP
5.8
\fIAutomatic regulation by pilots (group pilots, supergroup pilots,\fR
\fIetc.)\fR
.sp 9p
.RT
.PP
In carrier systems, the presence of pilots (line pilots, group
pilots, supergroup pilots,\ etc.) makes it possible to supervise transmission,
to keep track of short\(hyduration phenomena where necessary and to give
the
alarm if there are large variations in level.
.PP
Regulation by pilots and the way such regulation (manual or automatic)
is carried out has a decisive effect on transmission stability. In addition
to regulation by line pilots, with which wideband transmission systems
are
normally equipped, it may be necessary to regulate the group links themselves
(group links, supergroup links,\ etc.), both to achieve adequate stability
for the circuits formed from the groups and to reduce system overloading
risks
due to the existence of unduly high line levels.
.bp
.PP
Automatic regulation of links is a convenient means to meet the
requirements for the values of M and S of the pilot levels as stated under
\(sc\ 2 above. Therefore, automatic regulators should be fitted into a
link when
these limits cannot be achieved by other means.
.PP
However, when setting up a link the need for fitting automatic
regulators cannot be determined solely by these requirements. It is also
necessary to take practical considerations into account such as those given
in the Annex to this Recommendation.
.PP
In the case of through\(hyconnection points of group, supergroup, etc.
links, the insertion of automatic regulators prevents overloading of sections
further down the line. If a link is through\(hyconnected several times
and several regulators have to be inserted for the same direction of transmission
to meet the conditions of \(sc\ 2.2 above, the first insertion should be
made at the first through\(hyconnection point requiring regulation in that
direction of
transmission. A regulator should be inserted at the through\(hyconnection point
nearest the frontier (in the outgoing direction) when there are one or more
other through\(hyconnection points before this point on the same link.
This is to ensure that the level of the signals entering the next country
is kept within the prescribed limits.
.RT
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation M.160)
.sp 9p
.RT
.ce 0
.ce 1000
\fBPractical aspects to be considered\fR
.sp 1P
.RT
.ce 0
.ce 1000
\fBwhen determining the need for regulators\fR
.ce 0
.PP
When setting up a link the need for fitting regulators cannot be determined
solely by the requirements of \(sc\ 2 above of this Recommendation. It
is necessary to take the following practical considerations into account.
.sp 1P
.RT
.PP
A.1
In order to establish that a link meets the stability
requirements of this Recommendation it is either necessary to conduct long\(hyterm
tests at the time of setting up the link or to accept measurements made
on
similar links, that is, to predict the performance.
.sp 9p
.RT
.PP
If the former method is adopted, then, in the case of a link
passing in transit through the territory of a third Administration it is
probable that transit charges will apply from the date the link is set
up. In any event, the cooperation of the distant terminal Administration
will be
required and this may not be readily forthcoming.
.PP
If the latter method is adopted and the stability requirements are not
met, then the problem will arise of taking the link out of service to fit
a
regulator and to reline the link. This could entail a substantial loss of
revenue and will require distant end cooperation.
.RT
.PP
A.2
It is unusual for a supergroup to be provided with all five
groups allocated from the outset and it cannot be assumed that these groups
will end at the same point as the supergroup. In any case, if a group that
ends at the same point is changed to a through\(hygroup, then, unless a
supergroup
regulator has already been fitted, it may be necessary to interrupt service
to fit a regulator and reline the supergroup link.
.sp 9p
.RT
.PP
A.3
Consideration also has to be given to the restoration
requirements when deciding to fit regulators to supergroup links. Lack
of such regulators may seriously hamper restoration arrangements.
.sp 9p
.RT
.PP
A.4
Frequent rearrangements occur on international routes and are outside the
control of the distant Administration.
.sp 9p
.RT
.sp 2P
.LP
\fBReferences\fR
.sp 1P
.RT
.LP
[1]
CCITT Supplement \fIStatistical theory requirements\fR , Green Book,
Vol.\ IV.2, Supplement No.\ 1.6, ITU, Geneva,\ 1973.
.LP
[2]
CCITT Recommendation \fIArrangement of carrier equipment\fR , Vol.\ III,
Rec.\ G.231.
.LP
[3]
CCITT Supplement \fIVibration testing\fR , Green Book, Vol.\ IV.2, Supplement
No.\ 2.9, ITU, Geneva,\ 1973.
.LP
[4]
CCITT Recommendation \fILine stability of cable systems\fR , Vol.\ III,
Rec.\ G.214.
.bp
.sp 2P
.LP
\fBRecommendation\ M.250\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBUSE\ OF\ CCITT\ MAN\(hyMACHINE\ LANGUAGE\ (MML)\ FOR\ MAINTENANCE\fR
.EF '% Fascicle\ IV.1\ \(em\ Rec.\ M.250''
.OF '''Fascicle\ IV.1\ \(em\ Rec.\ M.250 %'
.ce 0
.sp 1P
.LP
\fB1\fR \fBMML as an instrument of maintenance\fR
.sp 1P
.RT
.sp 1P
.LP
1.1
\fIIntroduction\fR
.sp 9p
.RT
.PP
This Recommendation provides an introduction to the subject of MML as an
instrument of maintenance.
.PP
MML is a stored program controlled (SPC) facility which can operate only
within a computer controlled environment. When considering international
telephone system maintenance this will generally mean an SPC controlled
exchange or network.
.PP
MML is the medium used by the operations and maintenance staff to
communicate with the exchange control processor and vice versa
.FS
The
structure, syntax and semantics of MML are fully described in the Series\ Z
Recommendations published in Volume\ VI. Recommendation\ Z.311 describes the
basis of the CCITT man\(hymachine language and its fields of application.
It also identifies the content of the other Series\ Z Recommendations all
of which are addressed to the implementors of such languages rather than
to the
users.
.FE
.
.PP
The purposes of this Recommendation are to:
.RT
.LP
\(em
bring to the attention of the user the range of functions and facilities
offered by MML in the field of maintenance;
.LP
\(em
identify the full range of MML functions and facilities
provided to deal with maintenance;
.LP
\(em
define a standard terminology to describe the conditions that can exist
within an SPC network.
.PP
The objectives, tests and measurements for the maintenance of
circuits between exchanges, remain as described in all relevant Series\ M
Recommendations. This Recommendation does not seek to supplant existing
.LP
Recommendations nor to provide alternative methods or values for maintenance
but to give guidance on how the use of MML might be applied to existing
standards and procedures.
.sp 1P
.LP
1.2
\fIDefinition of\fR
\fIMML functions\fR
.sp 9p
.RT
.PP
MML functions are those system functions which provide the MML user with
the means of control of system functions by MML. The word \*Qcontrol\*U
is
assumed to include all types of inputs and outputs.
.PP
Any MML function can be subdivided into a general part which relates to
items such as the syntax check, information transmission control,\ etc.,
and an application part which relates to the job in hand.
.PP
The relationship between actual jobs to be performed, MML functions
and system functions is shown in Figure\ 1/M.250.
.RT
.LP
.rs
.sp 8P
.ad r
\fBFigure 1/M.250, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
1.3
Although the purpose of this Recommendation is to cover the
whole maintenance field, the following paragraphs deal only with maintenance
of circuits between exchanges. The rest is for further study.
.sp 9p
.RT
.sp 2P
.LP
\fB2\fR \fBList of
\fBsystem functions associated with the maintenance\fR
\fBof circuits between exchanges\fR
.sp 1P
.RT
.PP
Table 1/M.250 presents a list of functions associated with the
maintenance of circuits between exchanges which are considered to be
controllable by means of MML.
.RT
.ce
\fBH.T. [T1.250]\fR
.ce
TABLE\ 1/M.250
.ce
\fBList of system functions\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(12p) | lw(168p) .
1 {
Tests/measurements of one circuit or a group of circuits and
associated equipments
}
.T&
cw(12p) | lw(168p) .
2 {
Observation and supervision of circuits and associated equipments
between exchanges
}
.T&
cw(12p) | lw(168p) .
3 {
Control of the status of a circuit or a group of circuits and associated
equipments
}
.T&
cw(12p) | lw(168p) .
4 Analysis of maintenance data
.T&
cw(12p) | lw(168p) .
5 {
Administration and control of maintenance reports
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTable [T1.250], p.\fR
.sp 1P
.RT
.ad b
.RT
.PP
The broad categories of system function shown in Table 1/M.250
relate to the activities engaged in by all Administrations with a
responsibility for the maintenance of circuits interconnecting exchanges.
The application of these activities will vary between Administrations as
will the proportion of such activities that are performed by some degree
of
mechanization (partial or fully automatic).
.PP
System functions 4 and 5 may have such broad application that the
extent of on\(hyline and off\(hyline treatment must be considered carefully
by each Administration in relation to its requirements.
.RT
.sp 2P
.LP
\fB3\fR \fBList of MML functions\fR
.sp 1P
.RT
.PP
Table 2/M.250 represents the list of MML functions necessary to
control the system functions given in Table\ 1/M.250. The table presents the
functions at their most basic level and does not necessarily represent the
actual command structure of any real implementation of the man\(hymachine
language.
.PP
Each of the MML functions in the list could be implemented either by providing
a separate and distinctive command, or several MML functions of the list
could be implemented by means of a single command.
.PP
For example, in one implementation of MML, a single command CREATE, in
which the object to be created will be defined as a parameter of the command
(e.g.\ A MEASUREMENT), will perform internally precisely the same activities
and functions as another implementation which provides a separate and distinctive
command for the creation of each object (e.g.\ CREATE A MEASUREMENT). In
this
way the list of MML functions can be said to be system independent, as each
function exists either implicitly or explicitly regardless of the methods of
implementation chosen for particular systems.
.PP
The list of MML functions shown in Table 2/M.250 have a wider
application than the maintenance of circuits between exchanges. Many of the
functions identified are common to a wide range of maintenance and operational
requirements, and the contents of the table should be considered whenever
changes to the maintenance strategy and procedures are necessitated by the
introduction or extension of MML in the maintenance field.
.RT
.sp 2P
.LP
\fB4\fR \fBTerminology\fR
.sp 1P
.RT
.PP
The MML terminology to be used for maintenance is a subject for
further study.
.PP
\fINote\fR \ \(em\ Recommendation Z.341, Glossary of terms (for the
man\(hymachine language), suggests that a function may be considered as an
\*Qaction upon an object\*U, e.g.\ create a routine test. Actions e.g.\
\*QCREATE\*U are defined in the Appendix\ I to Recommendation\ Z.333 which
describes the
methodology for the specification of a man\(hymachine interface. Objects
and their modifiers, e.g.\ routine test, are the subject of further study.
.bp
.RT
.ce
\fBH.T. [T2.250]\fR
.ce
TABLE\ 2/M.250
.ce
\fBList of MML functions\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(24p) | lw(156p) .
1.1\ Create a routine test
.T&
cw(24p) | lw(156p) .
1.2\ Create a routine measurement
.T&
cw(24p) | lw(156p) .
1.3\ Create a test set
.T&
cw(24p) | lw(156p) .
1.4\ Create a measurement set
.T&
cw(24p) | lw(156p) .
1.5\ Create a list of circuits
.T&
cw(24p) | lw(156p) .
1.6\ Create a time data list
.T&
cw(24p) | lw(156p) .
1.7\ Create an output media list
.T&
cw(24p) | lw(156p) .
1.8\ Delete a test set
.T&
cw(24p) | lw(156p) .
1.9\ Delete a measurement set
.T&
cw(24p) | lw(156p) .
1.10 Delete a list of circuits
.T&
cw(24p) | lw(156p) .
1.11 Delete a time data list
.T&
cw(24p) | lw(156p) .
1.12 Delete an output media list
.T&
cw(24p) | lw(156p) .
1.13 Interrogate a test
.T&
cw(24p) | lw(156p) .
1.14 Interrogate a test set
.T&
cw(24p) | lw(156p) .
1.15 Interrogate a measurement
.T&
cw(24p) | lw(156p) .
1.16 Interrogate a measurement set
.T&
cw(24p) | lw(156p) .
1.17 {
Interrogate a list of circuits
}
.T&
cw(24p) | lw(156p) .
1.18 Interrogate a time data list
.T&
cw(24p) | lw(156p) .
1.19 {
Interrogate an output media list
}
.T&
cw(24p) | lw(156p) .
1.20 Activate a routine test
.T&
cw(24p) | lw(156p) .
1.21 {
Activate a routine measurement
}
.T&
cw(24p) | lw(156p) .
1.22 Activate an on\(hydemand test
.T&
cw(24p) | lw(156p) .
1.23 {
Activate an on\(hydemand measurement
}
.T&
cw(24p) | lw(156p) .
1.24 Deactivate a routine test
.T&
cw(24p) | lw(156p) .
1.25 {
Deactivate a routine measurement
}
.T&
cw(24p) | lw(156p) .
1.26 {
Output the results of a routine test
}
.T&
cw(24p) | lw(156p) .
1.27 {
Output the results of a routine measurement
}
.T&
cw(24p) | lw(156p) .
2.1\ {
Interrogate the status of a circuit(s) and/or associated equipment(s)
}
.T&
cw(24p) | lw(156p) .
2.2\ {
Input trouble or restoral report
}
.T&
cw(24p) | lw(156p) .
3.1\ {
Remove a circuit (or group of circuits)
}
.T&
cw(24p) | lw(156p) .
3.2\ {
Restore a circuit (or group of circuits)
}
.T&
cw(24p) | lw(156p) .
4.1\ {
Activate maintenance analysis functions
}
.T&
cw(24p) | lw(156p) .
4.2\ {
Deactivate maintenance analysis functions
}
.T&
cw(24p) | lw(156p) .
4.3\ Change analysis thresholds
.T&
cw(24p) | lw(156p) .
4.4\ Change analysis groups
.T&
cw(24p) | lw(156p) .
4.5\ {
Interrogate analysis thresholds
}
.T&
cw(24p) | lw(156p) .
4.6\ Interrogate analysis groups
.T&
cw(24p) | lw(156p) .
4.7\ {
Allow, inhibit, initialize a threshold
}
.T&
cw(24p) | lw(156p) .
5.1\ {
Sort trouble or restoral reports
}
.T&
cw(24p) | lw(156p) .
5.2\ Move reports to other files
.T&
cw(24p) | lw(156p) .
5.3\ Browse report files
.T&
cw(24p) | lw(156p) .
5.4\ Create summary reports
.T&
cw(24p) | lw(156p) .
5.5\ Activate a report on demand
.T&
cw(24p) | lw(156p) .
5.6\ Activate a report on routine
.T&
cw(24p) | lw(156p) .
5.7\ {
Deactivate a report on routine
}
.T&
cw(24p) | lw(156p) .
5.8\ Change report classification
.T&
cw(24p) | lw(156p) .
5.9\ Output summary reports
.T&
cw(24p) | lw(156p) .
5.10 Route output of reports
_
.TE
.nr PS 9
.RT
.ad r
\fBTable\ [2.250], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp